Issue escalation by management unit

ABSTRACT

Monitoring the health status of a distributed storage network (DSN) can include obtaining first status information indicating a first operational status of at least one DSN memory at a first point in time, the first operational status indicating one or more first operational issues. Second status information indicating a second operational status of the at least one DSN memory at a later point in time is obtained. The first operational status is compared to the second operational status to identify outstanding operational issues, e.g. issues that are indicated in both the first status information and the second status information. Each outstanding operational issue is mapped to an impact category, and an escalation level is determined based, at least in part, on the impact category. Notifications for a particular issue can be sent based on the escalation level for that issue.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present U.S. Utility patent application claims priority pursuant to 35 U.S.C. §119(e) to U.S. Provisional Application No. 62/301,214, entitled “ENHANCING PERFORMANCE OF A DISPERSED STORAGE NETWORK,” filed Feb. 29, 2016, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility patent application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND OF THE INVENTION

Technical Field of the Invention

This invention relates generally to computer networks and more particularly to dispersing error encoded data.

Description of Related Art

Computing devices are known to communicate data, process data, and/or store data. Such computing devices range from wireless smart phones, laptops, tablets, personal computers (PC), work stations, and video game devices, to data centers that support millions of web searches, stock trades, or on-line purchases every day. In general, a computing device includes a central processing unit (CPU), a memory system, user input/output interfaces, peripheral device interfaces, and an interconnecting bus structure.

As is further known, a computer may effectively extend its CPU by using “cloud computing” to perform one or more computing functions (e.g., a service, an application, an algorithm, an arithmetic logic function, etc.) on behalf of the computer. Further, for large services, applications, and/or functions, cloud computing may be performed by multiple cloud computing resources in a distributed manner to improve the response time for completion of the service, application, and/or function. For example, Hadoop is an open source software framework that supports distributed applications enabling application execution by thousands of computers.

In addition to cloud computing, a computer may use “cloud storage” as part of its memory system. As is known, cloud storage enables a user, via its computer, to store files, applications, etc. on an Internet storage system. The Internet storage system may include a RAID (redundant array of independent disks) system and/or a dispersed storage system that uses an error correction scheme to encode data for storage.

If left unattended or unmonitored, dispersed storage systems may quickly fall into disrepair as memory devices and storage units continue to fail without replacement. Left unchecked, data loss is inevitable.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a dispersed or distributed storage network (DSN) in accordance with the present invention;

FIG. 2 is a schematic block diagram of an embodiment of a computing core in accordance with the present invention;

FIG. 3 is a schematic block diagram of an example of dispersed storage error encoding of data in accordance with the present invention;

FIG. 4 is a schematic block diagram of a generic example of an error encoding function in accordance with the present invention;

FIG. 5 is a schematic block diagram of a specific example of an error encoding function in accordance with the present invention;

FIG. 6 is a schematic block diagram of an example of a slice name of an encoded data slice (EDS) in accordance with the present invention;

FIG. 7 is a schematic block diagram of an example of dispersed storage error decoding of data in accordance with the present invention;

FIG. 8 is a schematic block diagram of a generic example of an error decoding function in accordance with the present invention;

FIG. 9 is a schematic block diagram of an embodiment of a dispersed storage network in accordance with the present invention; and

FIG. 10 is a flowchart illustrating an example of prioritizing repair issue escalation in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a dispersed, or distributed, storage network (DSN) 10 that includes a plurality of computing devices 12-16, a managing unit 18, an integrity processing unit 20, and a DSN memory 22. The components of the DSN 10 are coupled to a network 24, which may include one or more wireless and/or wire lined communication systems; one or more non-public intranet systems and/or public internet systems; and/or one or more local area networks (LAN) and/or wide area networks (WAN).

The DSN memory 22 includes a plurality of storage units 36 that may be located at geographically different sites (e.g., one in Chicago, one in Milwaukee, etc.), at a common site, or a combination thereof. For example, if the DSN memory 22 includes eight storage units 36, each storage unit is located at a different site. As another example, if the DSN memory 22 includes eight storage units 36, all eight storage units are located at the same site. As yet another example, if the DSN memory 22 includes eight storage units 36, a first pair of storage units are at a first common site, a second pair of storage units are at a second common site, a third pair of storage units are at a third common site, and a fourth pair of storage units are at a fourth common site. Note that a DSN memory 22 may include more or less than eight storage units 36. Further note that each storage unit 36 includes a computing core (as shown in FIG. 2, or components thereof) and a plurality of memory devices for storing dispersed error encoded data.

Each of the computing devices 12-16, the managing unit 18, and the integrity processing unit 20 include a computing core 26, which includes network interfaces 30-33. Computing devices 12-16 may each be a portable computing device and/or a fixed computing device. A portable computing device may be a social networking device, a gaming device, a cell phone, a smart phone, a digital assistant, a digital music player, a digital video player, a laptop computer, a handheld computer, a tablet, a video game controller, and/or any other portable device that includes a computing core. A fixed computing device may be a computer (PC), a computer server, a cable set-top box, a satellite receiver, a television set, a printer, a fax machine, home entertainment equipment, a video game console, and/or any type of home or office computing equipment. Note that each of the managing unit 18 and the integrity processing unit 20 may be separate computing devices, may be a common computing device, and/or may be integrated into one or more of the computing devices 12-16 and/or into one or more of the storage units 36.

Each interface 30, 32, and 33 includes software and hardware to support one or more communication links via the network 24 indirectly and/or directly. For example, interface 30 supports a communication link (e.g., wired, wireless, direct, via a LAN, via the network 24, etc.) between computing devices 14 and 16. As another example, interface 32 supports communication links (e.g., a wired connection, a wireless connection, a LAN connection, and/or any other type of connection to/from the network 24) between computing devices 12 and 16 and the DSN memory 22. As yet another example, interface 33 supports a communication link for each of the managing unit 18 and the integrity processing unit 20 to the network 24.

Computing devices 12 and 16 include a dispersed storage (DS) client module 34, which enables the computing device to dispersed storage error encode and decode data (e.g., data 40) as subsequently described with reference to one or more of FIGS. 3-8. In this example embodiment, computing device 16 functions as a dispersed storage processing agent for computing device 14. In this role, computing device 16 dispersed storage error encodes and decodes data on behalf of computing device 14. With the use of dispersed storage error encoding and decoding, the DSN 10 is tolerant of a significant number of storage unit failures (the number of failures is based on parameters of the dispersed storage error encoding function) without loss of data and without the need for a redundant or backup copies of the data. Further, the DSN 10 stores data for an indefinite period of time without data loss and in a secure manner (e.g., the system is very resistant to unauthorized attempts at accessing the data).

In operation, the managing unit 18 performs DS management services. For example, the managing unit 18 establishes distributed data storage parameters (e.g., vault creation, distributed storage parameters, security parameters, billing information, user profile information, etc.) for computing devices 12-14 individually or as part of a group of user devices. As a specific example, the managing unit 18 coordinates creation of a vault (e.g., a virtual memory block associated with a portion of an overall namespace of the DSN) within the DSN memory 22 for a user device, a group of devices, or for public access and establishes per vault dispersed storage (DS) error encoding parameters for a vault. The managing unit 18 facilitates storage of DS error encoding parameters for each vault by updating registry information of the DSN 10, where the registry information may be stored in the DSN memory 22, a computing device 12-16, the managing unit 18, and/or the integrity processing unit 20.

The managing unit 18 creates and stores user profile information (e.g., an access control list (ACL)) in local memory and/or within memory of the DSN memory 22. The user profile information includes authentication information, permissions, and/or the security parameters. The security parameters may include encryption/decryption scheme, one or more encryption keys, key generation scheme, and/or data encoding/decoding scheme.

The managing unit 18 creates billing information for a particular user, a user group, a vault access, public vault access, etc. For instance, the managing unit 18 tracks the number of times a user accesses a non-public vault and/or public vaults, which can be used to generate a per-access billing information. In another instance, the managing unit 18 tracks the amount of data stored and/or retrieved by a user device and/or a user group, which can be used to generate a per-data-amount billing information.

As another example, the managing unit 18 performs network operations, network administration, and/or network maintenance. Network operations includes authenticating user data allocation requests (e.g., read and/or write requests), managing creation of vaults, establishing authentication credentials for user devices, adding/deleting components (e.g., user devices, storage units, and/or computing devices with a DS client module 34) to/from the DSN 10, and/or establishing authentication credentials for the storage units 36. Network administration includes monitoring devices and/or units for failures, maintaining vault information, determining device and/or unit activation status, determining device and/or unit loading, and/or determining any other system level operation that affects the performance level of the DSN 10. Network maintenance includes facilitating replacing, upgrading, repairing, and/or expanding a device and/or unit of the DSN 10.

The integrity processing unit 20 performs rebuilding of ‘bad’ or missing encoded data slices. At a high level, the integrity processing unit 20 performs rebuilding by periodically attempting to retrieve/list encoded data slices, and/or slice names of the encoded data slices, from the DSN memory 22. For retrieved encoded slices, they are checked for errors due to data corruption, outdated version, etc. If a slice includes an error, it is flagged as a ‘bad’ slice. For encoded data slices that were not received and/or not listed, they are flagged as missing slices. Bad and/or missing slices are subsequently rebuilt using other retrieved encoded data slices that are deemed to be good slices to produce rebuilt slices. The rebuilt slices are stored in the DSN memory 22.

FIG. 2 is a schematic block diagram of an embodiment of a computing core 26 that includes a processing module 50, a memory controller 52, main memory 54, a video graphics processing unit 55, an input/output (TO) controller 56, a peripheral component interconnect (PCI) interface 58, an IO interface module 60, at least one IO device interface module 62, a read only memory (ROM) basic input output system (BIOS) 64, and one or more memory interface modules. The one or more memory interface module(s) includes one or more of a universal serial bus (USB) interface module 66, a host bus adapter (HBA) interface module 68, a network interface module 70, a flash interface module 72, a hard drive interface module 74, and a DSN interface module 76.

The DSN interface module 76 functions to mimic a conventional operating system (OS) file system interface (e.g., network file system (NFS), flash file system (FFS), disk file system (DFS), file transfer protocol (FTP), web-based distributed authoring and versioning (WebDAV), etc.) and/or a block memory interface (e.g., small computer system interface (SCSI), internet small computer system interface (iSCSI), etc.). The DSN interface module 76 and/or the network interface module 70 may function as one or more of the interface 30-33 of FIG. 1. Note that the IO device interface module 62 and/or the memory interface modules 66-76 may be collectively or individually referred to as IO ports.

FIG. 3 is a schematic block diagram of an example of dispersed storage error encoding of data. When a computing device 12 or 16 has data to store it disperse storage error encodes the data in accordance with a dispersed storage error encoding process based on dispersed storage error encoding parameters. The dispersed storage error encoding parameters include an encoding function (e.g., information dispersal algorithm, Reed-Solomon, Cauchy Reed-Solomon, systematic encoding, non-systematic encoding, on-line codes, etc.), a data segmenting protocol (e.g., data segment size, fixed, variable, etc.), and per data segment encoding values. The per data segment encoding values include a total, or pillar width, number (T) of encoded data slices per encoding of a data segment (i.e., in a set of encoded data slices); a decode threshold number (D) of encoded data slices of a set of encoded data slices that are needed to recover the data segment; a read threshold number (R) of encoded data slices to indicate a number of encoded data slices per set to be read from storage for decoding of the data segment; and/or a write threshold number (W) to indicate a number of encoded data slices per set that must be accurately stored before the encoded data segment is deemed to have been properly stored. The dispersed storage error encoding parameters may further include slicing information (e.g., the number of encoded data slices that will be created for each data segment) and/or slice security information (e.g., per encoded data slice encryption, compression, integrity checksum, etc.).

In the present example, Cauchy Reed-Solomon has been selected as the encoding function (a generic example is shown in FIG. 4 and a specific example is shown in FIG. 5); the data segmenting protocol is to divide the data object into fixed sized data segments; and the per data segment encoding values include: a pillar width of 5, a decode threshold of 3, a read threshold of 4, and a write threshold of 4. In accordance with the data segmenting protocol, the computing device 12 or 16 divides the data (e.g., a file (e.g., text, video, audio, etc.), a data object, or other data arrangement) into a plurality of fixed sized data segments (e.g., 1 through Y of a fixed size in range of Kilo-bytes to Tera-bytes or more). The number of data segments created is dependent of the size of the data and the data segmenting protocol.

The computing device 12 or 16 then disperse storage error encodes a data segment using the selected encoding function (e.g., Cauchy Reed-Solomon) to produce a set of encoded data slices. FIG. 4 illustrates a generic Cauchy Reed-Solomon encoding function, which includes an encoding matrix (EM), a data matrix (DM), and a coded matrix (CM). The size of the encoding matrix (EM) is dependent on the pillar width number (T) and the decode threshold number (D) of selected per data segment encoding values. To produce the data matrix (DM), the data segment is divided into a plurality of data blocks and the data blocks are arranged into D number of rows with Z data blocks per row. Note that Z is a function of the number of data blocks created from the data segment and the decode threshold number (D). The coded matrix is produced by matrix multiplying the data matrix by the encoding matrix.

FIG. 5 illustrates a specific example of Cauchy Reed-Solomon encoding with a pillar number (T) of five and decode threshold number of three. In this example, a first data segment is divided into twelve data blocks (D1-D12). The coded matrix includes five rows of coded data blocks, where the first row of X11-X14 corresponds to a first encoded data slice (EDS 1_1), the second row of X21-X24 corresponds to a second encoded data slice (EDS 2_1), the third row of X31-X34 corresponds to a third encoded data slice (EDS 3_1), the fourth row of X41-X44 corresponds to a fourth encoded data slice (EDS 4_1), and the fifth row of X51-X54 corresponds to a fifth encoded data slice (EDS 5_1). Note that the second number of the EDS designation corresponds to the data segment number.

Returning to the discussion of FIG. 3, the computing device also creates a slice name (SN) for each encoded data slice (EDS) in the set of encoded data slices. A typical format for a slice name 80 is shown in FIG. 6. As shown, the slice name (SN) 80 includes a pillar number of the encoded data slice (e.g., one of 1-T), a data segment number (e.g., one of 1-Y), a vault identifier (ID), a data object identifier (ID), and may further include revision level information of the encoded data slices. The slice name functions as, at least part of, a DSN address for the encoded data slice for storage and retrieval from the DSN memory 22.

As a result of encoding, the computing device 12 or 16 produces a plurality of sets of encoded data slices, which are provided with their respective slice names to the storage units for storage. As shown, the first set of encoded data slices includes EDS 1_1 through EDS 5_1 and the first set of slice names includes SN 1_1 through SN 5_1 and the last set of encoded data slices includes EDS 1_Y through EDS 5_Y and the last set of slice names includes SN 1_Y through SN 5_Y.

FIG. 7 is a schematic block diagram of an example of dispersed storage error decoding of a data object that was dispersed storage error encoded and stored in the example of FIG. 4. In this example, the computing device 12 or 16 retrieves from the storage units at least the decode threshold number of encoded data slices per data segment. As a specific example, the computing device retrieves a read threshold number of encoded data slices.

To recover a data segment from a decode threshold number of encoded data slices, the computing device uses a decoding function as shown in FIG. 8. As shown, the decoding function is essentially an inverse of the encoding function of FIG. 4. The coded matrix includes a decode threshold number of rows (e.g., three in this example) and the decoding matrix in an inversion of the encoding matrix that includes the corresponding rows of the coded matrix. For example, if the coded matrix includes rows 1, 2, and 4, the encoding matrix is reduced to rows 1, 2, and 4, and then inverted to produce the decoding matrix.

With reference to FIGS. 9 and 10 below, various embodiments capable of Issue Escalation by a Management Unit will be discussed. To decrease the likelihood that distributed storage memories will lose data due to a lack of monitoring or unperformed maintenance, one or more management units within a DSN memory can monitor the health status of themselves, and the other DS units that comprise the DSN memory. As issues are created, but not addressed, the management unit's progress through several configurable steps of increasing desperation. At the initial stages, it may be limited to events in a graphical user interface (GUI) or task lists sent to operators in the field. Should these events not be viewed in the user interface, or are not addressed by operators in the field, various embodiments can escalate the urgency of addressing the event. A chain of successive escalations might go through the following levels:

1. Operators in the field

2. Operator supervisors

3. System or Network Admins

4. Head of Storage

5. DSN Vendor (if third-party monitoring support is enabled)

6. CTO

7. CEO

How high up an issue is escalated may depend on the length of time an issue has gone unaddressed, the estimated risk level the data is subject to, when failure rates outpace repair rates on an ongoing or consistent basis, and the number of remaining management units that survive to perform this function. Note that the management units may be a function applied across storage units, so that the monitoring/reporting function is itself reliable. Alternatively, storage units themselves may proceed through successive escalation when the management unit appears unavailable or to have ceased in its functions.

FIG. 9 is a schematic block diagram of another embodiment of a dispersed storage network that includes a plurality of distributed storage and task (DST) processing units 90, 92, and D, the network 24 of FIG. 1, the distributed storage and task network (DSTN) managing unit 18 of FIG. 1, and a set of DST execution units 96, 98, and n. Each DST execution unit includes processing module 84, which is an example of computing core 26 of FIG. 2, and a plurality of memories 1-M. Each memory may be implemented utilizing memory, such as storage unit 36 of FIG. 1 The DSN functions to prioritize repair issue escalation.

In an example of operation of the prioritizing of the repair issue escalation, the DSTN managing unit 18 of FIG. 1 obtains status information 100, 102, and n from the set of DST execution units 96, 98, and n. The status information 100, 102, and n includes one or more of a failed memory device indicator, a scheduled replacement time frame for a memory device, etc. The obtaining includes one or more of interpreting a query response, interpreting a received error message, and receiving the status information. For example, the DSTN managing unit 18 of FIG. 1 receives status information 100, 102, and n from the DST execution units 96, 98, and n, where the status information 100 indicates that DST execution unit 96 has failed and the status information 102 indicates that memories 1-2 of the DST execution unit 98 have failed.

Having obtained the status information, the DSTN managing unit 18 of FIG. 1 compares the status information 100, 102, and n to the previous status information 100, 102, and n to produce, for each outstanding issue requiring repair, and outstanding issue age. For example, the DSTN managing unit 18 of FIG. 1 calculates a difference between time frames of issue discovery and a current timeframe to produce the age.

Having produced the issue age, for each outstanding issue, the DSTN managing unit 18 of FIG. 1 maps the outstanding issued to an impact category. The impact category includes one or more of slow performance, potential for data loss, etc. The mapping includes correlating outstanding issued to a corresponding impact category in accordance with a mapping template. For example, the DSTN managing unit 18 of FIG. 1 maps the failure of memory device 2 of the DST execution unit 96 to the data loss impact category.

Having the impact category, the DSTN managing unit 18 of FIG. 1, for each outstanding issue, determines an escalation level based on the corresponding impact category and issue age. The determining may be based on one or more of a template, an input from a manager, an interpretation of system registry information, and on previous issues and corresponding resolutions. For example, the DSTN managing unit 18 of FIG. 1 establishes a higher priority escalation level for the DST execution unit 98 when the memories 1-2 have failed.

Having determined the escalation level, for each outstanding issue, the DSTN managing unit 18 of FIG. 1 issues one or more notifications 94 in accordance with the escalation level. The issuing includes identifying a notification recipient based on the escalation level in accordance with an escalation list (e.g., field technicians up to senior managers within an organization responsible for repairs), generates the notification 94 to include one or more of the status information 100, 102, and n, the issue age, the impact category, and the escalation level, and sends the notification 94 to the identified notification recipient. For example, the DSTN managing unit 18 of FIG. 1 sends a notification 94 to a local field service technician with regards to a failure of the memory 2 of the DST execution unit 96 and sends another notification 94 to a senior service manager with regards to the failure of the memories 1-2 of the DST execution unit 98 when a higher probability of data loss exists.

FIG. 10 is a flowchart illustrating an example of prioritizing repair issue escalation. The method includes block 118 where a processing module (e.g., of a distributed storage and task network (DSTN) managing unit) obtains status information for a set of storage units. The obtaining includes at least one of interpreting a query response, interpreting a received error message, and receiving the status information.

The method continues at block 120 where the processing module compares the status information to previous status information to produce, for each outstanding issue requiring repair, an outstanding issue age. For example, the processing module calculates a difference between time frames of issue discovery and a current timeframe to produce the age.

For each outstanding issue, the method continues at block 122 where the processing module maps the outstanding issued to an impact category. For example, the processing module maps the outstanding issued to the impact category in accordance with a mapping template.

For each outstanding issue, the method continues at block 124 where the processing module determines an escalation level based on the corresponding impact category and issue age. The determining may be based on one or more of a template, a manager input, and interpretation of system registry information, and on previous results of previous resolution of issues.

For each outstanding issue, the method continues at block 126 where the processing module issues one or more notifications in accordance with the escalation level. The issuing includes identifying a notification recipient based on the escalation level in accordance with an escalation list, generating the notification to include one or more of the status information, the issue age, the impact integrate, and the escalation level, and sending the notification to the identified notification recipient.

It is noted that terminologies as may be used herein such as bit stream, stream, signal sequence, etc. (or their equivalents) have been used interchangeably to describe digital information whose content corresponds to any of a number of desired types (e.g., data, video, speech, audio, etc. any of which may generally be referred to as ‘data’).

As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “configured to”, “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for an example of indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “configured to”, “operable to”, “coupled to”, or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item.

As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1. As may be used herein, the term “compares unfavorably”, indicates that a comparison between two or more items, signals, etc., fails to provide the desired relationship.

As may also be used herein, the terms “processing module”, “processing circuit”, “processor”, and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture.

One or more embodiments have been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claims. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claims. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

The one or more embodiments are used herein to illustrate one or more aspects, one or more features, one or more concepts, and/or one or more examples. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process may include one or more of the aspects, features, concepts, examples, etc. described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers and, as such, the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different ones.

Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of the embodiments. A module implements one or more functions via a device such as a processor or other processing device or other hardware that may include or operate in association with a memory that stores operational instructions. A module may operate independently and/or in conjunction with software and/or firmware. As also used herein, a module may contain one or more sub-modules, each of which may be one or more modules.

As may further be used herein, a computer readable memory includes one or more memory elements. A memory element may be a separate memory device, multiple memory devices, or a set of memory locations within a memory device. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. The memory device may be in a form a solid state memory, a hard drive memory, cloud memory, thumb drive, server memory, computing device memory, and/or other physical medium for storing digital information.

While particular combinations of various functions and features of the one or more embodiments have been expressly described herein, other combinations of these features and functions are likewise possible. The present disclosure is not limited by the particular examples disclosed herein and expressly incorporates these other combinations. 

What is claimed is:
 1. A method for use in a distributed storage network (DSN) including at least one DSN memory including a plurality of storage units storing encoded data slices, the method comprising: monitoring a health status of the DSN using at least one processor and associated memory included in the DSN, wherein monitoring the health status includes: obtaining first status information indicating a first operational status of the at least one DSN memory at a first point in time, the first operational status indicating one or more first operational issues; obtaining second status information indicating a second operational status of the at least one DSN memory at a second point in time, the second point in time being later than the first point in time, the second operational status indicating one or more second operational issues; comparing the first operational status to the second operational status to identify outstanding operational issues, wherein an outstanding operation issue is an operational issue indicated in both the first status information and the second status information; mapping each of the outstanding operational issues to an impact category; determining an escalation level for particular outstanding operational issues based, at least in part, on the impact category mapped to the particular outstanding operation issues; and issuing one or more notifications for the particular outstanding operational issues based, at least in part, on the escalation level determined for the particular outstanding operational issues.
 2. The method of claim 1, wherein monitoring the health status further includes: monitoring a health status of one or more management units included in the DSN.
 3. The method of claim 2, further comprising: determining a number of remaining management units capable of monitoring the health status of the DSN.
 4. The method of claim 1, wherein obtaining status information includes: interpreting a received error message.
 5. The method of claim 1, wherein comparing the first operational status to the second operational status to identify outstanding operational issues includes: determining an age of an outstanding operation issue by calculating a difference between a time at which the first operational issue was initially discovered, and a current time.
 6. The method of claim 1, wherein determining the escalation level is based on one or more of a template mapping impact category to escalation level, interpreting system registry information, or previous resolution information.
 7. The method of claim 1, wherein monitoring a health status of the DSN is performed by a management unit function applied across multiple different storage units included in the DSN.
 8. A distributed storage network (DSN) including: at least one DSN memory, the DSN memory including a plurality of storage units storing encoded data slice; at least one management unit implemented using at least one processor and associated memory, the management unit configured to monitor a health status of the DSN by: obtaining first status information indicating a first operational status of the at least one DSN memory at a first point in time, the first operational status indicating one or more first operational issues; obtaining second status information indicating a second operational status of the at least one DSN memory at a second point in time, the second point in time being later than the first point in time, the second operational status indicating one or more second operational issues; comparing the first operational status to the second operational status to identify outstanding operational issues, wherein an outstanding operation issue is an operational issue indicated in both the first status information and the second status information; mapping each of the outstanding operational issues to an impact category; determining an escalation level for particular outstanding operational issues based, at least in part, on the impact category mapped to the particular outstanding operation issues; and issuing one or more notifications for the particular outstanding operational issues based, at least in part, on the escalation level determined for the particular outstanding operational issues.
 9. The distributed storage network (DSN) of claim 8, wherein monitoring the at least one management unit is further configured to: monitor a health status of itself and one or more other management units included in the DSN.
 10. The distributed storage network (DSN) of claim 9, further comprising: determining a number of remaining management units capable of monitoring the health status of the DSN.
 11. The distributed storage network (DSN) of claim 8, wherein obtaining status information includes: interpreting a received error message.
 12. The distributed storage network (DSN) of claim 8, wherein comparing the first operational status to the second operational status to identify outstanding operational issues includes: determining an age of an outstanding operation issue by calculating a difference between a time at which the first operational issue was initially discovered, and a current time.
 13. The distributed storage network (DSN) of claim 8, wherein determining the escalation level is based on one or more of a template mapping impact category to escalation level, an interpretation of system registry information, or historical resolution information.
 14. The distributed storage network (DSN) of claim 8, wherein monitoring a health status of the DSN is performed by a management unit function applied across multiple different storage units included in the DSN.
 15. A management unit for use in a distributed storage network (DSN) including at least one DSN memory including a plurality of storage units storing encoded data slices, the management unit including: a processor; memory coupled to the processor and configured to store a program of instructions to be executed by the processor; the program of instructions configured to cause the management unit to monitor a health status of the DSN, the program of instructions including: at least one instruction to obtain first status information indicating a first operational status of the at least one DSN memory at a first point in time, the first operational status indicating one or more first operational issues; at least one instruction to obtain second status information indicating a second operational status of the at least one DSN memory at a second point in time, the second point in time being later than the first point in time, the second operational status indicating one or more second operational issues; at least one instruction to compare the first operational status to the second operational status to identify outstanding operational issues, wherein an outstanding operation issue is an operational issue indicated in both the first status information and the second status information; at least one instruction to map each of the outstanding operational issues to an impact category; at least one instruction to determine an escalation level for particular outstanding operational issues based, at least in part, on the impact category mapped to the particular outstanding operation issues; and at least one instruction to issue one or more notifications for the particular outstanding operational issues based, at least in part, on the escalation level determined for the particular outstanding operational issues.
 16. The management unit of claim 15, wherein the program of instructions further comprises: at least one instruction to monitor a health status of itself and one or more other management units included in the DSN.
 17. The management unit of claim 16, further comprising: at least one instruction to determine a number of remaining management units capable of monitoring the health status of the DSN.
 18. The management unit of claim 15, wherein obtaining status information includes: at least one instruction to interpret a received error message.
 19. The management unit of claim 15, wherein comparing the first operational status to the second operational status to identify outstanding operational issues includes: at least one instruction to determine an age of an outstanding operation issue by calculating a difference between a time at which the first operational issue was initially discovered, and a current time.
 20. The management unit of claim 15, wherein at least one instruction to determine the escalation level includes: at least one instruction to determine the escalation level based on one or more of a template mapping impact category to escalation level, an interpretation of system registry information, or historical resolution information. 